SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Technical communication</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Technical communication</span></span>

</h1>

</header>

<p>

<b>Technical communication</b> (or <b>tech comm</b>) is <a href="Communication" title="Communication">communication</a> of technical subject matter such as <a href="Engineering" title="Engineering">engineering</a>, <a href="Science" title="Science">science</a>, or <a href="Technology" title="Technology">technology</a> content. The largest part of it tends to be <a href="Technical_writing" title="Technical writing">technical writing</a>, though importantly it often requires aspects of <a href="Visual_communication" title="Visual communication">visual communication</a> (which in turn sometimes entails <a href="Technical_drawing" title="Technical drawing">technical drawing</a>, requiring more specialized training). Technical communication also encompasses oral delivery modes such as <a href="Presentation" title="Presentation">presentations</a> involving technical material. When technical communication occurs in workplace settings, it's considered a major branch of <a href="Professional_communication" title="Professional communication">professional communication</a>. In research or <a href="R%26D" class="mw-redirect" title="R&D">R&D</a> contexts (academic or industrial), it can overlap with <a href="Scientific_writing" title="Scientific writing">scientific writing</a>.

</p><p>Technical communication is used to convey scientific, engineering, or other technical information.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Individuals in a variety of contexts and with varied professional credentials engage in technical communication. Some individuals are designated as technical communicators or <a href="Technical_writer" title="Technical writer">technical writers</a> as their primary role; for some others, the role is inherently part of their technical position (e.g., engineers). In either case, these individuals utilize appropriate skills to research, document, and present technical information as needed. Technical communicators may use modalities including paper documents, digital files, audio and video media, and live delivery.

</p><p>The <a href="Society_for_Technical_Communication" title="Society for Technical Communication">Society for Technical Communication</a> defines the field as any form of communication that focuses on technical or specialized topics, communicates specifically by using technology, or provides instructions on how to do something.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-whirl_3-0" class="reference"><a href="#cite_note-whirl-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> More succinctly, the <a href="Institute_of_Scientific_and_Technical_Communicators" title="Institute of Scientific and Technical Communicators">Institute of Scientific and Technical Communicators</a> defines technical communication as factual communication, usually about products and services.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> The <a href="European_Association_for_Technical_Communication" title="European Association for Technical Communication">European Association for Technical Communication</a> briefly defines technical communication as "the process of defining, creating and delivering information products for the safe, efficient and effective use of products (technical systems, software, services)".<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>Whatever the definition of technical communication, the overarching goal of the practice is to create easily accessible information for a specific audience.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="As_a_profession">As a profession</h2></div>

<p>Technical communicators generally tailor information to a specific audience, which may be subject matter experts, consumers, end-users, etc. Technical communicators often work collaboratively to create <a href="Deliverable" title="Deliverable">deliverables</a> that include <a href="Online_help" title="Online help">online help</a>, user <a href="User_guide" title="User guide">manuals</a>, classroom training guides, computer-based training, <a href="White_paper" title="White paper">white papers</a>, government documents, <a href="Industrial_video" title="Industrial video">industrial videos</a>, <a href="Reference_card" title="Reference card">reference cards</a>, <a href="Data_sheet" class="mw-redirect" title="Data sheet">data sheets</a>, <a href="Journal_article" class="mw-redirect" title="Journal article">journal articles</a>, and patents.

<a href="Vocational_education" title="Vocational education">Technical</a> domains can be of any kind, including the soft and hard sciences, high technology including computers and software, and <a href="Consumer_electronics" title="Consumer electronics">consumer electronics</a>. Technical communicators often work with a range of <a href="Subject-matter_expert" title="Subject-matter expert">subject-matter experts</a> (SMEs) on these projects.

</p><p>Technical communication jobs include the following:<sup id="cite_ref-whirl_3-1" class="reference"><a href="#cite_note-whirl-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

<a href="API_writer" title="API writer">API writer</a>, e-learning author, <a href="Information_architect" class="mw-redirect" title="Information architect">information architect</a>, technical content developer, <a href="Technical_editor" class="mw-redirect" title="Technical editor">technical editor</a>, <a href="Technical_illustrator" class="mw-redirect" title="Technical illustrator">technical illustrator</a>, <a href="Technical_trainer" title="Technical trainer">technical trainer</a>, <a href="Technical_translator" class="mw-redirect" title="Technical translator">technical translator</a>, <a href="Technical_writer" title="Technical writer">technical writer</a>, usability expert, <a href="User_experience_designer" class="mw-redirect" title="User experience designer">user experience designer</a>, and user interface designer. Other jobs available to technical communicators include digital strategist, marketing specialist, and content manager.

</p><p>In 2015, the <a href="European_Association_for_Technical_Communication" title="European Association for Technical Communication">European Association for Technical Communication</a> published a competence framework for the professional field of technical communication.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>Much like technology and the world economy, technical communication as a profession has evolved over the last half-century.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> In a nutshell, technical communicators take the physiological research of a project and apply it to the communication process itself.

</p>

<div class="mw-heading mw-heading3"><h3 id="UX_design_in_technical_communications">UX design in technical communications</h3></div>

<p><a href="User_experience_design" title="User experience design">User experience (UX) design</a> has become more prominent in technical and professional communication (TPC) as companies look to develop content for a wide range of audiences and experiences.<sup id="cite_ref-:1_10-0" class="reference"><a href="#cite_note-:1-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p><p>The User Experience Professionals Association defines <a href="User_experience" title="User experience">user experience</a>, or UX, as "Every aspect of the user's interaction with a product, service, or company that make up the user's perception of the whole."<sup id="cite_ref-:2_11-0" class="reference"><a href="#cite_note-:2-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> Therefore, "user experience design as a discipline is concerned with all the elements that together make up that interface, including layout, visual design, text, brand, sound, and interaction."<sup id="cite_ref-:2_11-1" class="reference"><a href="#cite_note-:2-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup>

</p><p>It is now an expectation that technical communication skills should be coupled with UX design. As Verhulsdonck, Howard, and Tham state "...it is not enough to write good content. According to industry expectations, next to writing good content, it is now also crucial to design good experiences around that content." Technical communicators must now consider different platforms such as social media and apps, as well as different channels like web and mobile.<sup id="cite_ref-:1_10-1" class="reference"><a href="#cite_note-:1-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p><p>As Redish explains, TPC no longer writes content but "writes around the interface" itself as the user experience surrounding content is developed. This includes usable content customized to specific user needs, that addresses user emotions, feelings, and thoughts across different channels in a UX ecology.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-:1_10-2" class="reference"><a href="#cite_note-:1-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p><p>Lauer and Brumberger further assert, "…UX is a natural extension of the work that technical communicators already do, especially in the modern technological context of responsive design, in which content is deployed across a wide range of interfaces and environments."<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Content_creation">Content creation</h2></div>

<p>Technical communication is a task performed by specialized employees or consultants. For example, a professional writer may work with a company to produce a user manual. Some companies give considerable technical communication responsibility to other technical professionals—such as programmers, engineers, and scientists. Often, a professional technical writer edits such work to bring it up to modern technical communication standards.

</p><p>To begin the documentation process, technical communicators identify the audience and their information needs. The technical communicator researches and structures the content into a framework that can guide detailed development. As the body of information comes together, the technical communicator ensures that the intended audience can understand the content and retrieve the information they need. This process, known as the <a href="Writing_process" title="Writing process">writing process</a>, has been a central focus of writing theory since the 1970s, and some contemporary textbook authors apply it to technical communication. Technical communication is important to most professions, as a way to contain and organize information and maintain accuracy.

</p><p>The <a href="Technical_writing" title="Technical writing">technical writing</a> process is based on Cicero's five canons of <a href="Rhetoric" title="Rhetoric">rhetoric</a>, and can be divided into six steps:

</p>

<ol><li>Determine purpose and audience</li>

<li>Collect information (<a href="Inventio" title="Inventio">Invention</a>)</li>

<li>Organize and outline information (<a href="Dispositio" title="Dispositio">Arrangement</a>)</li>

<li>Write the first draft (<a href="Elocutio" title="Elocutio">Style</a>)</li>

<li>Revise and edit (<a href="Memoria" title="Memoria">Memory</a>)</li>

<li>Publish output (<a href="Pronuntiatio" title="Pronuntiatio">Delivery</a>)</li></ol>

<div class="mw-heading mw-heading3"><h3 id="Determining_purpose_and_audience">Determining purpose and audience</h3></div>

<p>All technical communication serves a particular purpose—typically to communicate ideas and concepts to an audience, or instruct an audience in a particular task. Technical communication professionals use various techniques to understand the audience and, when possible, test content on the target audience. For example, if bank workers don't properly post deposits, a technical communicator would review existing instructional material (or lack thereof), interview bank workers to identify conceptual errors, interview subject matter experts to learn the correct procedures, author new material that instructs workers in the correct procedures, and test the new material on the bank workers.

</p><p>Similarly, a sales manager who wonders which of two sites is better for a new store might ask a marketing professional to study the sites and write a report with recommendations. The marketing professional hands the report off to a technical communicator (in this case, a technical editor or technical writer), who edits, formats, and sometimes elaborates the document in order to make the marketing professional's expert assessment usable to the sales manager. The process is not one of knowledge transfer, but the accommodation of knowledge across fields of expertise and contexts of use. This is the basic definition of technical communication.

</p><p>Audience type affects many aspects of communication, from word selection and graphics use to style and organization. Most often, to address a particular audience, a technical communicator must consider what qualities make a text useful (capable of supporting a meaningful task) and usable (capable of being used in service of that task). A non-technical audience might misunderstand or not even read a document that is heavy with jargon—while a technical audience might crave detail critical to their work such as <a href="Vector_notation" title="Vector notation">vector notation</a>. Busy audiences often don't have time to read entire documents, so content must be organized for ease of searching—for example by frequent <a href="https://en.wiktionary.org/wiki/heading" class="extiw external" title="wikt:heading">headings</a>, <a href="White_space_(visual_arts)" title="White space (visual arts)">white space</a>, and other cues that guide <a href="Attention" title="Attention">attention</a>. Other requirements vary according to a particular audience's needs.

</p><p>Technical communicators may need to translate, globalize, or localize their documents to meet the needs of audiences in different linguistic and cultural markets. <b>Globalization</b> involves producing technical content that meets the needs of "as many audiences as possible," ideally an international audience.<sup id="cite_ref-:0_14-0" class="reference"><a href="#cite_note-:0-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> <b>Localization</b> adapts existing technical content to fit the "cultural, rhetorical, educational, ethical, [and] legal" expectations of users in a specific local context.<sup id="cite_ref-:0_14-1" class="reference"><a href="#cite_note-:0-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup>

</p><p>Technical communication, in the government, is particular and detailed. Depending on the segment of government (and country), the government component must follow distinct specifications. Information changes continuously and technical communications (technical manuals, interactive electronic technical manuals, technical bulletins, etc.) must be updated.

</p>

<div class="mw-heading mw-heading3"><h3 id="Collecting_information">Collecting information</h3></div>

<p>Technical communicators must collect all information that each document requires. They may collect information through primary (first-hand) research—or secondary research, using information from existing work by other authors. Technical communicators must acknowledge all sources they use to produce their work. To this end, technical communicators typically distinguish quotations, paraphrases, and summaries when taking notes.

</p>

<div class="mw-heading mw-heading3"><h3 id="Organizing_and_outlining_information">Organizing and outlining information</h3></div>

<p>Before writing the initial draft, the technical communicator organizes ideas in a way that makes the document flow well. Once each idea is organized, the writer organizes the document as a whole—accomplishing this task in various ways:

</p>

<ol><li>chronological: used for documents that involve a linear process, such as a step-by-step guide that describes how to accomplish something;</li>

<li>parts of an object: Used for documents that describe the parts of an object, such as a graphic showing the parts of a computer (keyboard, monitor, mouse, etc.);</li>

<li>simple to complex (or vice versa): starts with easy ideas and gradually goes into complex ideas;</li>

<li>specific to general: starts with many ideas, then organizes the ideas into sub-categories;</li>

<li>general to specific: starts with a few categories of ideas, then goes deeper.</li></ol>

<p>After organizing the whole document, the writer typically creates a final outline that shows the document's structure. Outlines make the writing process easier and save the author time.

</p>

<div class="mw-heading mw-heading3"><h3 id="Writing_the_first_draft">Writing the first draft</h3></div>

<p>After the outline is complete, the writer begins the first draft, following the outline's structure. Setting aside blocks of an hour or more, in a place free of distractions, helps the writer maintain a flow. Most writers prefer to wait until the draft is complete before any revising so they don't break their flow. Typically, the writer should start with the easiest section, and write the summary only after the body is drafted.

</p><p>The ABC (<i>a</i>bstract, <i>b</i>ody, and <i>c</i>onclusion) format can be used when writing a first draft of some document types. The abstract describes the subject so that the reader knows what the document covers. The body is the majority of the document and covers topics in depth. Lastly, the conclusion section restates the document's main topics. The ABC format can also apply to individual paragraphs—beginning with a topic sentence that states the paragraph's topic, followed by the topic, and finally, a concluding sentence.

</p>

<div class="mw-heading mw-heading3"><h3 id="Revising_and_editing">Revising and editing</h3></div>

<p>Once the initial draft is laid out, editing and revising can be done to fine-tune the draft into a final copy. Usability testing can be helpful to evaluate how well the writing and/or design meets the needs of end-users and to suggest improvements [<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>] Four tasks transform the early draft into its final form, suggested by Pfeiffer and Boogard:

</p>

<div class="mw-heading mw-heading4"><h4 id="Adjusting_and_reorganizing_content">Adjusting and reorganizing content</h4></div>

<p>In this step, the writer revises the draft to elaborate on topics that need more attention, shorten other sections—and relocate certain paragraphs, sentences, or entire topics.

</p>

<div class="mw-heading mw-heading4"><h4 id="Editing_for_style">Editing for style</h4></div>

<p>Good style makes writing more interesting, appealing, and readable. In general, the personal writing style of the writer is not evident in technical writing. Modern technical writing style relies on attributes that contribute to clarity: headings, lists, graphics; generous white space, short sentences, present tense, simple nouns, <a href="Active_voice" title="Active voice">active voice</a><sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup> (though some scientific applications still use the <a href="Passive_voice" title="Passive voice">passive voice</a>), second and third person as required

</p><p>Technical writing as a discipline usually requires that a technical writer use a <a href="Style_guide" title="Style guide">style guide</a>. These guides may relate to a specific project, product, company, or brand. They ensure that technical writing reflects formatting, punctuation, and general stylistic standards that the audience expects. In the United States, many consider the <i><a href="Chicago_Manual_of_Style" class="mw-redirect" title="Chicago Manual of Style">Chicago Manual of Style</a></i> the bible for general technical communication. Other style guides have their adherents, particularly for specific industries—such as the <i>Microsoft Style Guide</i> in some information technology settings.

</p>

<div class="mw-heading mw-heading4"><h4 id="Editing_for_grammar_and_punctuation">Editing for grammar and punctuation</h4></div>

<p>At this point, the writer performs a <i>mechanical edit</i>, checking the document for grammar, punctuation, common word confusions, passive voice, overly long sentences, etc.

</p>

<ul><li><a href="Digital_rhetoric" title="Digital rhetoric">Digital rhetoric</a></li>

<li><a href="Technical_definition" title="Technical definition">Technical definition</a></li>

<li><a href="Technical_editing" class="mw-redirect" title="Technical editing">Technical editing</a></li>

<li><a href="Technical_geography" title="Technical geography">Technical geography</a></li>

<li><a href="Technical_writing" title="Technical writing">Technical writing</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFJohnson-Sheehan2005" class="citation book cs1">Johnson-Sheehan, Richard (2005). <i>Technical Communication Today</i>. Longman. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-11764-9</bdi>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.stc.org/about-stc/defining-technical-communication/">Defining Technical Communication</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210123003809/https://www.stc.org/about-stc/defining-technical-communication/">Archived</a> 23 January 2021 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at the STC official website. Accessed 28 February 2018.</span>

</li>

<li id="cite_note-whirl-3"><span class="mw-cite-backlink">^ <a href="#cite_ref-whirl_3-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-whirl_3-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://techwhirl.com/what-is-technical-communications/">What is Technical Communications?</a> TechWhirl. Accessed 9 December 2014.</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.istc.org.uk/wp-content/uploads/2011/08/CareersLeaflet-v1-1.pdf">Thinking of a career in technical communication?</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160421114512/http://www.istc.org.uk/wp-content/uploads/2011/08/CareersLeaflet-v1-1.pdf">Archived</a> 21 April 2016 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at the ISTC official website. Last updated May 2012. Accessed 28 February 2013.</span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.technical-communication.org/technical-communication/defining-technical-communication.html">Defining Technical Communication</a> at the Tekom Europe official website. Last updated October 2015. Accessed 8 October 2015.</span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100524154910/http://www.tcanz.org.nz/Resources/Learn+About+Technical+Communication/Technical+Communication.html">What is Technical Communication?</a> at the official website of the Technical Communicators Association of New Zealand. Accessed 28 February 2013.</span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://competences.technical-communication.org/overview.html">Competence Framework for Technical Communication</a> at the Tekom Europe official website. Last updated October 2015. Accessed 8 October 2015.</span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite id="CITEREFMalone2007" class="citation journal cs1">Malone, E. A. (December 2007). "Historical Studies of Technical Communication in the United States and England: A Fifteen-Year Retrospection and Guide to Resources". <i>IEEE Transactions on Professional Communication</i>. <b>50</b> (4): <span class="nowrap">333–</span>351. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTPC.2007.908732">10.1109/TPC.2007.908732</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:39438169">39438169</a>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFKimball2016" class="citation journal cs1">Kimball, Miles A. (April 2016). "The Golden Age of Technical Communication". <i>Journal of Technical Writing and Communication</i>. <b>47</b> (3): <span class="nowrap">330–</span>358. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1177%2F0047281616641927">10.1177/0047281616641927</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:113266235">113266235</a>.</cite></span>

</li>

<li id="cite_note-:1-10"><span class="mw-cite-backlink">^ <a href="#cite_ref-:1_10-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:1_10-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:1_10-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFVerhulsdonckHowardTham2021" class="citation journal cs1">Verhulsdonck, Gustav; Howard, Tharon; Tham, Jason (21 September 2021). <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="http://journals.sagepub.com/doi/10.1177/00472816211041951">"Investigating the Impact of Design Thinking, Content Strategy, and Artificial Intelligence: A "Streams" Approach for Technical Communication and User Experience"</a></span>. <i>Journal of Technical Writing and Communication</i>. <b>51</b> (4): <span class="nowrap">468–</span>492. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1177%2F00472816211041951">10.1177/00472816211041951</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0047-2816">0047-2816</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:240552938">240552938</a>.</cite></span>

</li>

<li id="cite_note-:2-11"><span class="mw-cite-backlink">^ <a href="#cite_ref-:2_11-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:2_11-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFBaxterCourageCaine2015" class="citation cs2">Baxter, Kathy; Courage, Catherine; Caine, Kelly (2015), <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="https://dx.doi.org/10.1016/b978-0-12-800232-2.09986-7">"Acknowledgments"</a></span>, <i>Understanding your Users</i>, Elsevier, pp. <span class="nowrap">xxxiii–</span>xxxiv, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fb978-0-12-800232-2.09986-7">10.1016/b978-0-12-800232-2.09986-7</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780128002322</bdi><span class="reference-accessdate">, retrieved <span class="nowrap">7 November</span> 2021</span></cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text">Redish, Ginny. (30 September 2020). <i>UX Writing - A New Role for Technical Communicators? The MasterClass in TechComm for Society for Technical Communications</i> (Washington DC and Baltimore). [Apple podcast]. <a rel="nofollow" class="external free" href="https://podcasts.apple.com/us/podcast/ux-writing-a-new-role-for-technical-communicators/id1534090690?i=1000493180560">https://podcasts.apple.com/us/podcast/ux-writing-a-new-role-for-technical-communicators/id1534090690?i=1000493180560</a> </span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><cite id="CITEREFLauerBrumberger2016" class="citation journal cs1">Lauer, Claire; Brumberger, Eva (2016). "Technical Communication as User Experience in a Broadening Industry Landscape". <i>Technical Communication (Washington)</i>. <b>63</b> (3): 249.</cite></span>

</li>

<li id="cite_note-:0-14"><span class="mw-cite-backlink">^ <a href="#cite_ref-:0_14-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:0_14-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFBatovaClark2014" class="citation journal cs1">Batova, Tatiana; Clark, Dave (9 December 2014). <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="https://journals.sagepub.com/doi/10.1177/1050651914562472">"The Complexities of Globalized Content Management"</a></span>. <i>Journal of Business and Technical Communication</i>. <b>29</b> (2): <span class="nowrap">221–</span>235. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1177%2F1050651914562472">10.1177/1050651914562472</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:110090911">110090911</a>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite class="citation book cs1"><i>Solving problems in technical communication</i>. Johnson-Eilola, Johndan., Selber, Stuart A. Chicago. 26 December 2012. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-226-92406-9</bdi>. <a href="OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/783150285">783150285</a>.</cite><span class="cs1-maint citation-comment"><code class="cs1-code">{{cite book}}</code>: CS1 maint: location missing publisher (link) CS1 maint: others (link)</span></span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><a href="Gary_Blake" title="Gary Blake">Gary Blake</a> and <a href="Robert_W._Bly" title="Robert W. Bly">Robert W. Bly</a>, <i>The Elements of Technical Writing</i>, pg. 63. New York City: <a href="Macmillan_Publishers_(United_States)" class="mw-redirect" title="Macmillan Publishers (United States)">Macmillan Publishers</a>, 1993. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0020130856</bdi></span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><span class="noviewer" typeof="mw:File"></span> Media related to <a href="https://commons.wikimedia.org/wiki/Category:Technical_communication" class="extiw external" title="commons:Category:Technical communication">Technical communication</a> at Wikimedia Commons</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Communication_studies358" style="padding:3px"><table class="nowraplinks hlist mw-collapsible expanded navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="3"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Communication_studies358" style="font-size:114%;margin:0 4em"><a href="Communication_studies" title="Communication studies">Communication studies</a></div></th></tr><tr><td class="navbox-abovebelow" colspan="3"><div>

<ul><li><a href="History_of_communication_studies" title="History of communication studies">History</a></li>

<li><a href="Outline_of_communication" title="Outline of communication">Outline</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><div style="display: inline-block; line-height: 1.2em; padding: .1em 0;">Topics and<br> terminology</div></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Biocommunication_(science)" title="Biocommunication (science)">Biocommunication</a></li>

<li><a href="Broadcasting" title="Broadcasting">Broadcasting</a></li>

<li><a href="Communication" title="Communication">Communication</a></li>

<li><a href="Computer-mediated_communication" title="Computer-mediated communication">Computer-mediated communication</a></li>

<li><a href="Conversation" title="Conversation">Conversation</a></li>

<li><a href="History_of_communication" title="History of communication">History of communication</a></li>

<li><a href="Information" title="Information">Information</a></li>

<li><a href="Intercultural_communication" title="Intercultural communication">Intercultural</a></li>

<li><a href="Interpersonal_communication" title="Interpersonal communication">Interpersonal</a></li>

<li><a href="Intrapersonal_communication" title="Intrapersonal communication">Intrapersonal </a></li>

<li><a href="Journalism" title="Journalism">Journalism</a></li>

<li><a href="Literacy" title="Literacy">Literacy</a>

<ul><li><a href="Reading" title="Reading">Reading</a></li>

<li><a href="Writing" title="Writing">Writing</a></li></ul></li>

<li><a href="Mass_media" title="Mass media">Mass media</a></li>

<li><a href="Meaning_(philosophy)" title="Meaning (philosophy)">Meaning</a></li>

<li><a href="Means_of_communication" title="Means of communication">Media</a></li>

<li><a href="Media_ecology" title="Media ecology">Media ecology</a></li>

<li><a href="Meta-communication" title="Meta-communication">Meta-communication</a></li>

<li><a href="Models_of_communication" title="Models of communication">Models of communication</a></li>

<li><a href="New_media" title="New media">New media</a></li>

<li><a href="Nonverbal_communication" title="Nonverbal communication">Nonverbal communication</a></li>

<li><a href="Nonviolent_Communication" title="Nonviolent Communication">Nonviolent Communication</a></li>

<li><a href="Propaganda" title="Propaganda">Propaganda</a></li>

<li><a href="Public_relations" title="Public relations">Public relations</a></li>

<li><a href="Speech" title="Speech">Speech</a></li>

<li><a href="Symbol" title="Symbol">Symbol</a>

<li><a href="Telecommunications" title="Telecommunications">Telecommunications</a></li>

<li><a href="Text_and_conversation_theory" title="Text and conversation theory">Text and conversation theory</a></li></ul>

</div></td><td class="noviewer navbox-image" rowspan="3" style="width:1px;padding:0 0 0 2px"><div><span typeof="mw:File"></span></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Subfields</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Closed-loop_communication" title="Closed-loop communication">Closed-loop</a></li>

<li><a href="Communication_design" title="Communication design">Communication design</a></li>

<li><a href="Communication_theory" title="Communication theory">Communication theory</a></li>

<li><a href="Communicology" title="Communicology">Communicology</a></li>

<li><a href="Crisis_communication" title="Crisis communication">Crisis</a></li>

<li><a href="Climate_communication" title="Climate communication">Climate</a></li>

<li><a href="Cross-cultural_communication" title="Cross-cultural communication">Cross-cultural</a></li>

<li><a href="Development_communication" title="Development communication">Developmental</a></li>

<li><a href="Discourse_analysis" title="Discourse analysis">Discourse analysis</a></li>

<li><a href="Environmental_communication" title="Environmental communication">Environmental</a></li>

<li><a href="Study_of_global_communication" title="Study of global communication">Global</a></li>

<li><a href="Health_communication" title="Health communication">Health</a></li>

<li><a href="International_communication" title="International communication">International</a></li>

<li><a href="Media_studies" title="Media studies">Media studies</a></li>

<li><a href="Mediated_cross-border_communication" title="Mediated cross-border communication">Mediated cross-border</a></li>

<li><a href="Organizational_communication" title="Organizational communication">Organizational</a></li>

<li><a href="Political_communication" title="Political communication">Political</a></li>

<li><a href="Science_communication" title="Science communication">Science</a></li>

<li><a href="Visual_communication" title="Visual communication">Visual</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Scholars</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Theodor_W._Adorno" title="Theodor W. Adorno">Adorno</a></li>

<li><a href="Roland_Barthes" title="Roland Barthes">Barthes</a></li>

<li><a href="Gregory_Bateson" title="Gregory Bateson">Bateson</a></li>

<li><a href="Walter_Benjamin" title="Walter Benjamin">Benjamin</a></li>

<li><a href="Kenneth_Burke" title="Kenneth Burke">Burke</a></li>

<li><a href="Manuel_Castells" title="Manuel Castells">Castells</a></li>

<li><a href="Noam_Chomsky" title="Noam Chomsky">Chomsky</a></li>

<li><a href="Robert_T._Craig" title="Robert T. Craig">Craig</a></li>

<li><a href="Jacques_Ellul" title="Jacques Ellul">Ellul</a></li>

<li><a href="Walter_Fisher_(professor)" title="Walter Fisher (professor)">Fisher</a></li>

<li><a href="Vil%C3%A9m_Flusser" title="Vilém Flusser">Flusser</a></li>

<li><a href="Jos%C3%A9_Ortega_y_Gasset" title="José Ortega y Gasset">Gasset</a></li>

<li><a href="George_Gerbner" title="George Gerbner">Gerbner</a></li>

<li><a href="Erving_Goffman" title="Erving Goffman">Goffman</a></li>

<li><a href="J%C3%BCrgen_Habermas" title="Jürgen Habermas">Habermas</a></li>

<li><a href="Max_Horkheimer" title="Max Horkheimer">Horkheimer</a></li>

<li><a href="Aldous_Huxley" title="Aldous Huxley">Huxley</a></li>

<li><a href="Harold_Innis" title="Harold Innis">Innis</a></li>

<li><a href="Roman_Jakobson" title="Roman Jakobson">Jakobson</a></li>

<li><a href="Irving_Janis" title="Irving Janis">Janis</a></li>

<li><a href="Wendell_Johnson" title="Wendell Johnson">Johnson</a></li>

<li><a href="D._Lawrence_Kincaid" title="D. Lawrence Kincaid">Kincaid</a></li>

<li><a href="Walter_Lippmann" title="Walter Lippmann">Lippman</a></li>

<li><a href="Niklas_Luhmann" title="Niklas Luhmann">Luhmann</a></li>

<li><a href="Herbert_Marcuse" title="Herbert Marcuse">Marcuse</a></li>

<li><a href="Marshall_McLuhan" title="Marshall McLuhan">McLuhan</a></li>

<li><a href="Nick_Morgan" title="Nick Morgan">Morgan</a></li>

<li><a href="Vance_Packard" title="Vance Packard">Packard</a></li>

<li><a href="Charles_Sanders_Peirce" title="Charles Sanders Peirce">Peirce</a></li>

<li><a href="Neil_Postman" title="Neil Postman">Postman</a></li>

<li><a href="Nora_C._Quebral" title="Nora C. Quebral">Quebral</a></li>

<li><a href="I._A._Richards" title="I. A. Richards">Richards</a></li>

<li><a href="Everett_Rogers" title="Everett Rogers">Rogers</a></li>

<li><a href="Wilbur_Schramm" title="Wilbur Schramm">Schramm</a></li>

<li><a href="Claude_Shannon" title="Claude Shannon">Shannon</a></li>

<li><a href="James_W._Tankard_Jr." title="James W. Tankard Jr.">Tankard</a></li>

<li><a href="Deborah_Tannen" title="Deborah Tannen">Tannen</a></li>

<li><a href="Max_Wertheimer" title="Max Wertheimer">Wertheimer</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="3"><div>

<ul><li><span class="noviewer" typeof="mw:File"><span title="Category"></span></span> Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-18" href="https://en.wikipedia.org/wiki/?title=Technical_communication&oldid=1301233388">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>